Repository navigation
ci(release): create the GitHub release on tag pushes (hex.pm-only was only half the story) - #3
Merged
Merged
Conversation
…attern) The release workflow only published to hex.pm — nothing created the GitHub release, so tags produced no release objects (hex.pm got 0.1.1 but GitHub shows no v0.1.1 release). This ports the authify/authify create-release job, adapted: needs the publish job, contents:write permission, full-history checkout, notes from CHANGELOG.md's Keep-a-Changelog section for the version plus the commit list and a hex install line (instead of the Docker section).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The release workflow published to hex.pm but never created a GitHub release — the step didn't exist (nothing broken; the authify/authify repo carries a second
create-releasejob this library never got). This ports that job, adapted for a Hex library: triggers after the publish job succeeds,contents: writepermission, notes assembled from CHANGELOG.md's version section (Keep-a-Changelog) plus the commit list and the hex install line. The v0.1.1 release object itself is being created retroactively alongside this fix; future tags get it automatically.